home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990725-20000114
/
000329_news@columbia.edu _Wed Dec 8 05:04:33 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2000-01-13
|
4KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id FAA22908
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 8 Dec 1999 05:04:33 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id FAA28900
for kermit.misc@watsun.cc.columbia.edu; Wed, 8 Dec 1999 05:01:34 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
Date: Wed, 8 Dec 1999 00:14:34 -0700
From: <Use-Author-Address-Header@[127.1]>
Message-ID: <TCPSMTP.19.12.8.0.14.34.2375661496.5936642@kincyb.com>
Subject: screen / c-kermit notes
Organization: mail2news@nym.alias.net
To: kermit.misc@columbia.edu
(sent to comp.protocols.kermit.misc,
plug-discuss@plug.phoenix.az.us)
Below is an example from /etc/syslog.conf showing how
to send system logging to a virtual console as
Jim Dennis (LinuxCare/Linux Gazette) described in his
talk while at PLUG (Phoenix, AZ, USA) last month.
Just uncomment the 'daemon...' parts and set the
/dev/ttyX part to point to the desired virtual console
you want to watch the system logging on.
#
# I like to have messages displayed on the console, but only on a virtual
# console I usually leave idle.
#
#daemon,mail.*;\
# news.=crit;news.=err;news.=notice;\
# *.=debug;*.=info;\
# *.=notice;*.=warn /dev/tty8
# to this:
daemon,mail.*;\
news.=crit;news.=err;news.=notice;\
*.=debug;*.=info;\
*.=notice;*.=warn /dev/tty48
I recently wanted to do the same thing with my C-Kermit
session logging. (this could apply to any program that
keeps some kind of log, but this was the particular program
I wanted to do this with.) Trying to do this directly
to one of the normal virtual consoles, from a non-root
userid ran into all kinds of permission problems.
I then tried starting one of the other programs Jim Dennis
was enthusiastic about, 'screen', and tried sending the
kermit logging to it and again ran into permission problems.
A method I found that did work was to set up a link to
one of the screen supported virtual links:
$ln /dev/ttya2 portal
# start screen
$screen
$^A ^C # activating ttya1
$^A ^C # activating ttya2
$^A 1 # go to console #1 (ttya1)
$kermit # starting c-kermit
C-kermit> log session portal # to simply send logging to ttya2
or
log session {| tee portal | tee session.raw | ansi2text.sed > session.txt}
to get fancy with it.
(At least this worked on my Debian 2,1 system. :-) )
ttya2 now keeps a pristine copy of the most recent screenfull of
connect mode interaction, ungrunged by trips from the connect terminal
session to the kermit command line and back.
The documentation for 'screen' prominently warns about problems using
screen with Kermit (and z-modem) transfers since the screen escape
character, ^A is the same as the kermit packet framing character ^A.
More recent versions of C-Kermit have the capability to change
the start of frame character, as is documented in
"Using C-Kermit", 2nd edition on pages 217-219, using
the
set {send,receive} start-of-packet ^<some character>
command, so this should be a minor inconvenience for
serious use.
One other thing I do is use to the little documented 'tty'
command, in my bash startup scripts, to capture the
console in use and stick in my prompt so it's easier to
know which one I'm in.
($console = `tty`)
Much thanks to Jim Dennis for his willingness to share
his time, knowledge and enthusiasm. I met him again at
Sky Harbor airport the Friday after he spoke at ASU,
and he was graciously answering questions almost up
to the moment of boarding his plane!
Regards, Dallas E. Legan
dallasii
@
kincyb
.
com
leganii
@
surfree
.
com